What should Vift AI Studio look at?
Choose what to check, what to look for and how often. Everything is read on this computer.
Sign in so your plan comes back after a reinstall or on a new computer.
Finish signing in in your browser — this moves on by itself.
It joins this scan in the same tab, without using another of your plan's tabs. Only a part of the same app can join.
Choose what to check, what to look for and how often. Everything is read on this computer.
authorized_keys.403.X-Forwarded-For. Say where the site is hosted in Settings → Cloud blocking — Cloudflare, AWS, Azure, Google Cloud, your own server's firewall or anywhere else — and banned addresses are blocked there too.vift shield --to=… instead.Your plan, and what it lets you run.
What every scan and every monitor does, and the extras that stay off until you turn them on, because they send something off this computer or need a sign-in.
Get told about attacks when you are not looking at this window. Email, and Slack, Discord, Teams or Google Chat through a webhook, are the quickest to set up, and each has a phone app. WhatsApp works too, but takes the longest.
Paste an incoming-webhook URL. Slack, Discord, Microsoft Teams and Google Chat are recognised and get a readable message; any other https address gets the alert as signed JSON.
All four come from the WhatsApp Cloud API on Meta for Developers — the most involved channel. For a quicker phone alert, use Email or a Slack/Discord webhook above.
Token must be a permanent Meta System User token (Business Settings → System Users → Add → Generate, scope whatsapp_business_messaging); the Getting-Started one expires in 24 hours. Template must be approved in WhatsApp Manager — without one, an alert outside the 24-hour window is accepted but never delivered.
When the guard blocks an attacker, it can block them where your site is hosted too — so they never reach your server.
In Cloudflare: My Profile → API Tokens → Create Token → Custom token. Give it Zone → Firewall Services → Edit and Zone → Zone Settings → Edit, for this site only. It is kept on this computer and never shown here again.
A JSON POST for each decision, signed like an alert webhook (x-vift-signature):
{"event": "block", "address": "203.0.113.9", "minutes": 60, "until": "…", "reason": "repeated attacks"}
{"event": "unblock", "address": "203.0.113.9"}
{"event": "flood", "state": "start"} … {"event": "flood", "state": "end"}
Every block is followed by its unblock when its time is up or the guard stops, so nothing is left behind.
Sign in so your plan comes back after a reinstall or on a new computer.
Finish signing in in your browser — this updates by itself.
Signing in is coming soon. Scanning, buying and your licence all work without it.
For a team that runs a Vift AI Studio server of its own. Connected, the findings you accept or waive here are shared with everybody on that server, and a scan can be sent to it from the Send menu. Scanning, buying and your licence never use it — on your own, leave this closed.
Scans leave this machine only when you send them, never as whole files.
Optional. An AI model reads your code as well, and can catch mistakes the built-in checks don’t know about. What it finds is marked as the AI’s opinion. Choose where the AI runs:
Let Claude, Cursor or VS Code read your scan results and start scans for you.
http://127.0.0.1:7879/mcp/<your key>
Works while this app is open. Copying it switches the connection on.
The same tools over REST, for your own programs and scripts. The key goes in Authorization: Bearer …
Not created yet
Whether monitoring keeps going when you close the window or restart the computer.
How roomy the window looks, and what stays on screen.
What Vift AI Studio does with your code, this computer and you. The full policy, with the address each thing goes to, is on the website.
--offline turns it off.~/.vift